Core Concepts

Understand the key building blocks of Mative Cloud Fleet Management: orders, payloads, drivers, vehicles, fleets, and how they relate.

Orders

An Order represents a delivery task or service job with:

• Status progressing through a defined lifecycle (created → dispatched → started → completed)
• A Payload containing pickup/dropoff locations and items
• Assigned driver and vehicle
• An Order Configuration defining the workflow and proof-of-delivery method

Order Statuses

Status	Always Present?	Meaning
created	Yes	Order awaiting dispatch
dispatched	Yes	Order sent to driver
started	Yes	Driver accepted and working
canceled	Yes	Order cancelled before completion
completed	Configurable	Order delivered

The first four statuses are static (cannot be removed). The completed status can be replaced by any custom activity with its complete flag set to true.

Between started and completion, the intermediate steps a driver moves through are defined by the activity flow of the Order Configuration.

Payload

A Payload defines:

• Pickup location — origin for item collection
• Dropoff destination — primary delivery destination
• Return address — optional return-to-sender location
• Entities — individual items with tracking numbers, dimensions, weight, barcode/SKU
• Waypoints — intermediate stops for multi-drop routes (each may require individual proof of delivery)

Order Configuration

An Order Configuration is a reusable template that defines:

• The activity flow (status sequence)
• Entity field definitions
• Proof-of-delivery method (signature, photo, QR code, custom data)
• Custom order-level fields

Multiple configurations support different service types (standard delivery, pickup & delivery, cold chain, etc.).

Drivers

A Driver executes orders using the FM Mobile mobile app, storing:

• Real-time location (latitude, longitude, heading, speed)
• Online/offline status
• Current job assignment
• Skills and constraints (max distance, time window, required skills)
• Shift schedule

Vehicles

A Vehicle is a fleet asset storing:

• Make, model, year, body type, color
• Plate number and VIN
• Capacity (weight in kg, volume in m³)
• Real-time location
• Status (active, inactive, maintenance, offline)

Vehicles connect to the Connectivity module for telematics tracking and to the Maintenance module for service records.

Fleets

A Fleet logically groups drivers and vehicles by:

• Geographic zone or service area
• Service type (express, standard, overnight)
• Shift (morning fleet, evening fleet)
• Vendor or subcontractor

Hierarchical structures allow sub-fleets. The Orchestrator uses fleet membership for order allocation.

Places

A Place is a reusable saved location with:

• Full address details and precise coordinates
• Contact phone number
• Links to Contacts
• Live map appearance

Contacts

Contacts are the businesses and people in your operations:

• Customer — recipient of the delivery
• Supplier — origin of items
• Facilitator — coordinates the order

Vendors

Vendors are third-party carriers or service providers with their own driver pools and fleets. Integrated Vendors (e.g., partner platforms) relay orders to partner APIs and fetch quotes automatically.

Service Areas & Zones

A Service Area is a polygon boundary; Zones are sub-regions within it. Used for:

• Service rate scoping
• Fleet assignment filtering
• Geofence event triggering

Orchestrator

The Orchestrator is a multi-phase planner that converts unassigned orders into committable plans through composable phases: Assign Vehicles → Optimize Routes → Assign Drivers. Preview and commit when satisfied, or run single phases independently.

Manifests

After Orchestrator commitment, a Manifest is created per driver — an ordered stop list with estimated distances and arrival times representing the driver's shift delivery plan.

How It All Connects

Order Config ──────────────────────── defines activity flow + entity fields
     │
     ▼
  Order ──── Payload ── Pickup / Dropoff / Entities / Waypoints
     │           │
     │           └── TrackingNumber (per entity)
     │
     ├── Driver (assigned)
     ├── Vehicle (assigned)
     ├── ServiceQuote (pricing)
     ├── Route (calculated directions)
     ├── Proofs (signature / photo / QR)
     └── Manifest (after Orchestrator commit)
        └── ManifestStop (each order in the manifest)